PD ROM 1/PD ROM Volume I - Macintosh Software from BMUG (1988).iso/Electronic Messages/USEnet Digests/USEnet Vol. 3/USEnet 3.080

Internet Message Format | 1988-04-08 | 27.4 KB | [TEXT/ttxt]

Date: Sat 10 Oct 87 12:25:56-EDT
From: Jeff Shulman <SHULMAN@SDR>
Subject: Usenet Mac Digest V3 #80

Usenet Mac Digest     Saturday, October 10, 1987     Volume 3 : Issue 80

Today's Topics:
     Generic serial printer driver.
     Moonlighting
     Re: HyperCard-hypertext
     Re: C problem
     Re: SE and mouse tracking
     Re: Hypercard question
     Help on a LSP program
     What is .Bout for?!?
     Re: Virtual Memory with the Mac OS
     Re: Hypercard question
     Re: Hypercard again (radio button)
     A Macintalk Question
     Re: What is .Bout for?!?
     Re: When to HLock
     Re: Help wanted:  MacinTalk parameters
     Re: Help on a LSP program
     Crunched shell
     Re: Keycaps--Mathematical Symbols
     Re: Status of Apple UNIX ?
     Re: What is .Bout for?!?
     Cricket Graph bug?
     comments on tape backup sold by `apda' requested

----------------------------------------------------------------------

From: [e-mail] (Earle R. Horton)
Subject: Generic serial printer driver.
Date: 7 Oct 87 03:13:03 GMT
Organization: disorganized

The generic serial printer driver I posted to comp.binaries.mac has an
incompatibility with MicroSoft Word, VersaTerm PRO and maybe some other
programs.  The problem arises because these programs expect the routine
PrOpenPage() (in the printer code) to do a SetPort to the printing port
before it returns.  This feature of the printing code is not documented
anywhere by Apple, as far as I know, and so I didn't put it in my
driver.

Whether PrOpenPage is required do this, or whether the authors of these
programs just took advantage of a feature of Apple's drivers that they
found, is only known to the folks at Cupertino, who aren't sayin'.

To get a copy of the printer driver that works with MicroSoft Word and
VersaTerm PRO (and has some other, small, bugs fixed) follow the
directions in the comp.binaries.mac posting.  (I'm asking for bug
reports, people who send me good ones get a free copy of the final
version of the printer driver.)

--
*********************************************************************
*Earle R. Horton, H.B. 8000, Dartmouth College, Hanover, NH 03755   *
*********************************************************************


------------------------------

From: [e-mail] (R.BRANDI)
Subject: Moonlighting
Date: 7 Oct 87 02:02:08 GMT
Organization: AT&T, Middletown NJ

Anybody else happen to notice that nice little Mac II featured
prominently on tonight's episode of Moonlighting?...

Ralph


    ====      | Disclaimer: Just `cuz I work on the Death Star,
 ==OOO=====   | that doesn't mean I speak for Darth Vader...
=OOOOOOO====  | Ralph Brandi, {ihnp4,mhuxt}!homxb!mtuxo!lzfme!ralph
=OOOOOOO====  | Kopykat (k) 1987, R.A.Brandi
 ==OOO=====   | All Rights Reserved, All Jams Preserved,
    ====      | All Nasty Comments Soundly Deserved...


------------------------------

From: [e-mail] (Robert Gardner)
Subject: Re: HyperCard-hypertext
Date: 7 Oct 87 23:47:22 GMT
Organization: Philips Research Labs, Sunnyvale, California

In article <[e-mail]> [e-mail] (Andrew V Jewell)
writes:
>My problem is that I need to get the next and previous word.
>"white" would go to one entry, but "white bread" is different and
>"egg white" is separate from those two.

You might try separating words like this with option-space (and do the
same in the dictionary). Option-space looks like a space (though it's
wider in some fonts) but doesn't usually cause word-breaking.

Robert Gardner


------------------------------

From: [e-mail] (Clith de T'nir a.k.a. Reid Ellis)
Subject: Re: C problem
Date: 5 Oct 87 23:39:31 GMT
Organization: Unicus Software Inc.

In article <[e-mail]> [e-mail] (J.S.Shapiro) writes:

    Now that we have different screen sizes, it no longer suffices to
    hardwire things like the screen width. A DA is not really allowed to
    call InitGraf. What can I do (assembler is ok) to find out the values
    of the screenBits rect?

DA's (and any non-'CODE' code, I think) are not allowed to access
Quickdraw's global variables. (thePort etc, or qd.* if you are using MPW
or Aztec C) (I didn't know Aztec used 'qd.' like MPW.  Is this new?) If
you consider multiple screen environments, there are two possible things
you want.
a) just "this" screen's rectangle
b) the bounding rectangle for all screens.

You can use 'GetWMGrPort(&grafptrVar);' which gives you
grafptrVar->portRect, which is a Rect that encloses the entire
multi-screen display space.

And I'm not sure, but I *think* that grafptrVar->portBits.bounds is be
the rectangle for just the "this" screen.

    This may be a MANX bug.

Nope, it's the way DAs work.

    Jds aondimo

--- Reid Ellis    mnetor!unicus![e-mail]


------------------------------

From: [e-mail] (Les Kay)
Subject: Re: SE and mouse tracking
Date: 8 Oct 87 02:24:37 GMT
Organization: The Big Electric Cat

In article <[e-mail]> [e-mail] (Martin Hall) writes:
>Is there a general problem with mouse tracking and Mac SEs?
>
>
Yes there is a problem, but I don't think Apple knows what the source
is... Fortunately, it is a rather minor problem.  It is, also, on the
Mac II....


--
===============================================================================
Jonathan Bing, Master (cheeser)            ...ihnp4!hoptoad!dasys1!cheeser
          Time flys like an Arrow, Fruit Flies like Bananas!
===============================================================================


------------------------------

From: [e-mail] (Dan Freedman)
Subject: Re: Hypercard question
Date: 5 Oct 87 14:03:00 GMT
Organization: U. of Calgary, Calgary, Ab.

Well, for any linked list, all you need is to store a pointer to the
next element somewhere in the current element.  In HyperCard, the
"pointer" is the card id of the next card (a number like '12345'), and
you may as well store it in a field on each card in your list (perhaps
called "next card").  You can make the card invisible by issuing the
'hide  field "next card"' command in the message window (this only need
be done once. Once the field is hidden, it will stay hidden until you
issue a 'show field "next card"' command).  You should probably also
tick off the "lock text" option for that field so that users can't
change it's contents even if they manage to make the field visible (you
can still change the field's contents from a script, even if lock text
is switched on).

Getting the name of the next card is quite easy if you create the cards
from a script:  something like this excerpt should do the trick.

    ...
    put the id of this card into oldcard
    doMenu "New Card"
    put the id of this card into field "next card" of card id oldcard
    -- note that "this card" changes during the doMenu "New Card" command.
    ...

The excerpt should be inserted in whatever script creates new cards for
your linked list.  Multiply linked lists can be handles in a similar
fashion. If your list must link cards across stacks, then you must also
store the name of the stack as well as the id number of the card.  The
command "this stack" will return the name of the current stack.

I hope this is helpful.

    Dan Freedman.
    University of Calgary Computer Science Department.


------------------------------

From: patel@smu
Subject: Help on a LSP program
Date: 5 Oct 87 17:49:00 GMT

I am writing an application (in Lightspeed Pascal) that displays various
types of objects of varying size and allows the user to move these
objects around.  Since the objects are of varying size, I cannot use
ICONs to represent them.  What is the best way of doing this?

If I use PICTs to draw these objects, then how do I detect that the user
has clicked inside a particular object?  How do I drag only the outline
of the object?

Any help would be appreciated.  Example source would be even better.

Nirav Patel


------------------------------

From: [e-mail] (Ted Johnson)
Subject: What is .Bout for?!?
Date: 6 Oct 87 20:31:23 GMT
Organization: Hewlett Packard  DTC

Could someone please tell me what a .Bout file is for?  A plain document
icon called .Bout appears every now and then in a folder full of PD
software.  Get Info... claims that it's 0k large, which seems pretty
strange.  Anyone care to venture forth with an illuminating explanation?

    -Ted

**********************************************************************
Ted C. Johnson
Hewlett Packard, Design Technology Center
Santa Clara, CA
[phone]
UUCP: ...hplabs!hpcea!hpcid!tedj
**********************************************************************

------------------------------

From: [e-mail] (Fred Fish)
Subject: Re: Virtual Memory with the Mac OS
Date: 5 Oct 87 21:33:35 GMT
Organization: Motorola Microcomputer Division

In article <[e-mail]> [e-mail] (Stew Rubenstein) writes:
>The wait states are already there.  Two of 'em.  The 851 doesn't add any more.
>As I understand it, it's a drop-in replacement for the fake MMU that's in
>there now.

On the back of a recent EE Times was an ad from Hamilton-Avnet for
something called an MC68020KIT, which included a 68851, 68020, and 68881
(all 16Mhz) for $399.  I ordered one, snarfed out the 68851 (actually an
XC68851) and popped it into my Mac-II.  As far as I can tell, everything
works exactly as before.  So yes, it does look like it is a drop in
replacement. I've since resold the remainder of the kit to someone who
could use the 020 and 881, so my net cost for the PMMU was about $100.
Now if I could just get A/UX...  :-(

-Fred
--
# Fred Fish    hao!noao!mcdsun!fnf    [phone]
# Motorola Computer Division, 2900 S. Diablo Way, Tempe, Az 85282  USA


------------------------------

From: [e-mail] (Dan Freedman)
Subject: Re: Hypercard question
Date: 6 Oct 87 20:39:00 GMT
Organization: U. of Calgary, Calgary, Ab.

In article <[e-mail]>, [e-mail] (Grobbins)
writes:
> I'm trying to go to cards by a name composed of a string constant
> and a variable number, as in
>   go to card "Sheetnum"&snum    -- and variants, incl. putting "x"&y in parens
> but Hypercard usually fails to go to the proper, or any, card.
> This occurs only (or primarily) in scripts; if I execute the same
> line in the message window, Hypercard takes me to the proper card
> without complaining.

Hmm, I went to the home stack, and tried the following:
    CMD-2 (to get away from the home card)
    put "e" into f
    go to card "hom"&f

from the message box.  It did not work.  I then tried:
    go to card "hom" & e
(note the spacing).  It worked.  I then made a button in the card before the home card
and put the following into the script:
    on mouseUp
        put "e" into f
        go to card "hom" & f
    end mouseUp

and tried the button.  It worked perfectly.  Could it be that you are having
problems because of the way you are spacing your arguments?  What do you mean when
you say that HyperCard "usually" fails?  I tried my button 5 or 6 times, and it
worked each time.

    Dan Freedman
    University of Calgary Computer Science Department

------------------------------

From: [e-mail] (Jan Harrington)
Subject: Re: Hypercard again (radio button)
Date: 8 Oct 87 12:39:32 GMT
Organization: Scholastech, Inc., Waltham, Mass.

How you handle the highlighting depends on whether you've checked Auto
hilight when you defined the button.  If Auto hilight is checked (in
that dialog box you get for buttons), then Hypercard will take care of
turning the button on and off.  You can check the button's state with
something like:

    if autoHilite of button ID XX is true then
        .....

Replace the XX, of course, with the right button ID or ID XX with the
button's name if the script is attached to something other than the
button itself.  If the script is attached to the button itself, then you
don't need the button identifier.

If Auto hilight isn't selected, then you must attach a script to each
button which detects mouseup events, checks the current hilite state,
and then sets the button accordingly:

    if hilite is true then
        set hilite false
    else
        set hilite true
    .....

In most cases, using Auto hilite is certainly easier!

Jan Harrington, sysop
Scholastech Telecommunications
ihnp4!husc6!amcad!stech!sysop

------------------------------

From: [e-mail]
Subject: A Macintalk Question
Date: 8 Oct 87 19:26:27 GMT
Organization: Yale University, New Haven, CT

>From: James Spohrer <spohrer-james>

Is it possible to get at the waveform (i.e., as an array of integers)
that the Macintalk driver generates?

I realize this may be a stupid question if some chips just takes phoneme
codes and converts them to an analog signal. However, if the phonemes to
waveform conversion is handled in software then it seems reasonable to
suspect that one could get ones hand on the digital waveform. Any one
know how?

Thanks,
Jim Spohrer
SPOHRER@YALE
432-1227
-------

------------------------------

From: [e-mail] (Eric K. Olson)
Subject: Re: What is .Bout for?!?
Date: 8 Oct 87 14:53:06 GMT
Organization: Lexington Software Design

In a recent article Ted Johnson writes:
>Could someone please tell me what a .Bout file is for?  A plain
>document icon called .Bout appears every now and then in a folder full
>of PD software.  Get Info... claims that it's 0k large, which seems pretty
>strange.  Anyone care to venture forth with an illuminating explanation?
>

This is a problem with some PD software (most of it quite old).  .Bout
is the name of one of the serial ports on the Macintosh.  If the
software tries to open it the wrong way, it will create a file.  Also,
the SUMacC (Stanford University Mac C - cross compiler, runs on a VAX)
compiler, I think, opens this file under cerain circumstances (very few
people use this compiler any more).

In summary, it's a bug, and can be safely ignored.

-Eric


Eric K. Olson     [e-mail]     harvard!endor!olson     D0760
   (Name)                (ArpaNet)                 (UseNet)        (AppleLink)

------------------------------

From: [e-mail] (David Fry)
Subject: Re: When to HLock
Date: 8 Oct 87 15:41:32 GMT
Organization: Harvard Math Department

In article <[e-mail]> [e-mail] (Tom
Carstensen) writes:
>Question: Do you need to HLock in the following
>kind of situation?:
>
>TEHandle TheText;
>lines = (**TheText).nLines

No, because you're only accessing memory and assigning it to a stack
variable, lines.  You need to HLock when memory may be moved.  Inside
Mac has a list of Toolbox calls that can move memory, but if you don't
want to look it up you can call HLock before a Toolbox routine (better
to look it up).

Suppose, however that you wanted to create a NewWindow and the refcon
was going to be the number of lines in the TEHandle, then you must HLock
before calling the NewWindow because NewWindow may move memory:

MoveHHi(TheText);
HLock(TheText);
myWindow = NewWindow( , ,...,(**TheText).nLines );
HUnlock(TheText);

"How to Write Macintosh Software" by Scott Kastner (sp?) is a great
source for tidbits like this.

David Fry                [e-mail]
Department of Mathematics        [e-mail]
Harvard University            ...!harvard!huma1!fry
Cambridge, MA  02138

------------------------------

From: [e-mail] (Tim Wilson)
Subject: Re: Help wanted:  MacinTalk parameters
Date: 8 Oct 87 15:09:41 GMT
Organization: Rochester Institute of Technology, Rochester, NY

In article <[e-mail]> [e-mail] (Ted Johnson)
writes:
>Can someone please tell me what the max and min ranges are for the
>MacinTalk subroutines SpeechRate() and SpeechPitch()?

>From the MacinTalk Documentation for MacinTalk 1.1 (1/31/86):
SpeechPitch - thePitch >  65 to 500 or 0 to just change theMode.
SpeechRate - theRate > 85 to 425


------------------------------

From: [e-mail] (Richard Siegel)
Subject: Re: Help on a LSP program
Date: 8 Oct 87 17:35:44 GMT
Organization: THINK Technologies, Inc., Bedford, MA

This isn't a LSP-specific problem, but I'll take a shot at it anyway.

You can probably set up a list of regions, and use PtInRgn() to see
which particular region landed in, and you can use DragGrayRgn() to drag
a gray outline of the region along with your mouse hit...

        --Rich

------------------------------

From: [e-mail] (John Draper)
Subject: Crunched shell
Date: 8 Oct 87 10:05:52 GMT
Organization: Whole Earth Lectronic Link, Sausalito CA

   I'm compiling up quite an impressive list of goodies to include in
"the crunched shell".   Quite a few people have submitted very valuable
source code listings for such things as MIDI drivers and some other
stuff.    I have responded to EVERY one who has mailed and requested
information.   If you mailed to me,  and haven't gotten a reply,  it
means my "mailer" hasn't generated a proper path to your site.

   I have enough in the list to keep an army of programmers busy for the
next 30 years,  so I'm going to be rather selective in choosing which
features I want to include in the first "cut".

   Because of the Hackers 3.0 Conference coming up this weekend,  I'm
holding off publishing the list of features until after I've submitted
it to the attendees this weekend.    By then,  I'll have a pretty good
idea of what I should include.   I suspect that I'll be starting the
"shell" consolidation while at Hackers 3.0.

   I also hacked up a piece of code that writes C code, given a dialog
resource.    This should save me considerable time.    It basically does
the following:

1.  Asks for a resource file containing a Dialog.
2.  Allows user to select:  Pascal or C,  LightSpeed or MPW.
3.  It goes out there and looks at the DITL for the Dialog,  and using
    a code "Template" stored in a standard TEXT file,  it generates
    C or Pascal Source code that handles the Dialog.   It currently
    handles MODAL,  but MODELESS is also planned.

3.  It creates a C or Pascal function with the same name as the
    DLOG resource,  and #defines constants representing the
    DITL items with the same names as the DITL resource.

4.  It "builds" up the "case" statements and commenting where you
    can add your button handling code.

  All templates and "STR#" resources live in the application.   For
instance,  the names of the files you "#include" are stored in "STR#"
resources so you can modify them.   It then makes substitutions gotten
from the actual resource during the code generation phase.

  I'll be using this program to generate the SHELL program,  and
probably wind up including the "Code generation" part in the SHELL.   By
the time the first "cut" is released,  It should be pretty well tested.

  One of the things I HATED about Mac programming,  is to go looking for
Dialog handling code, and hacking it up to meed my needs.   Now, I don't
have to do it.    I plan on doing the following code generators:

1.  Desk accessory shell
2.  generic Application shell - A "Starter upper".
3.  Modal and Modeless dialogs.

   The "application shell" generator will go out and "look" at the menu
resources,  and create a "do_command()" function with all the necessary
"case" statements where you can add your OWN code for your own purposes.
A "GetNextEvent" or "WaitNextEvent" loop will be generated,  and
generic update, activate, inDrag,  inGrow code will be generated.
Naturally,  your applications needs might be  different,  and I plan on
allowing options to be selected by a dialog for customization.

    One question I have for anyone out there.....  Does anyone know if a
RAMDISK exists that can survive a "cold reset" for a Mac II like the
Levco Prodigy Mac??   Or is that some special hardware hack?? I suppose
some modifications might be needed to keep the power on during the
reset.

   A lot of people have been asking me about our Programmers Network,
and requesting information.   I was wondering if I should post a SHORT
posting explaining what we do without making it sound like an (ughh!)
commercial.   It IS non-commercial.

John Draper
Programmers Network
....ihnp4!ptsfa!well!crunch

------------------------------

From: [e-mail] (Dan Graifer)
Subject: Re: Keycaps--Mathematical Symbols
Date: 8 Oct 87 17:45:52 GMT
Organization: UCSD Office of Academic Computing

In article <[e-mail]> [e-mail] (D.W.Dougherty) writes:
>I just opened the box to my Mac last Saturday and started playing
>around with MacWrite.  I noticed, much to my dismay, that there is
>little support of mathematical symbols.  I do an awful lot of writing
>which involves some pretty heavy mathematics and I need that flexa-
>bility.  Can anybody recommend a package that supports just about
>every mathematical symbol you could think of??  It may certainly
>be PD.
>
>Thank you.
>
>        David W. Dougherty
>        {...ihnp4...}!attunix!dwd


There are three classes of solutions to this problem:

1.  If you only need one symbol at any horizontal location on a line,
just use the Symbol Font supplied with your Mac.  Use the Keycaps DA
(shrink your document window, and leave the DA open on the desktop) to
find symbol/keyboard correspondence.

2.  Use your favorite paint/draw program (the latter is better for
editting) to create your equations, and copy/paste them to your wp
document.  This will get easier when MultiFinder is released.

3.  There are several commercial packages that are essentially
specialized  draw programs for editting mathematical symbols.  MS Word
3.0x has a limited similer capability built in.

    MacEqn
        Desk Accessory $44.95
        Software Recognition Technologies
        110 University Park
        Rochester NY 14620
        [phone]

    MathType
        Desk Accessory or Application $149
        Design Science, Inc.
        6475-B E. Pacific Coast Highway
        Suite 392
        Long Beach, CA 90803
        [phone]

    MathWriter
        Application   $49.95?
        Cooke Publications
        P.O. Box 4448
        Ithaca, NY  14852
        [phone] x 15 (NY 1-800-435-4438 x 15) or [phone]

    Expressionist
        ?  $54.95
        Allan Bonadio Associates
        1579 Dolores St.
        San Francisco, CA 94110

You may be able to beat these prices.  Try calling MacConnection (the
most reputable of the mail-order houses) [phone]

I have no connection with any of the above companies
Good luck
                              Dan Graifer
                              [e-mail]
Disclaimer: Nobody ever listens to me anyways; Why should they start now?

------------------------------

From: root@sbcs (Root)
Subject: Re: Status of Apple UNIX ?
Date: 7 Oct 87 13:17:15 GMT
Organization: State University of New York at Stony Brook

Perhaps this is heresy, by has anyone out there thought of plunking
Sun's version of Unix onto the MAC-II?  Since I've heard that Sun now
has a "University Source" tape, and given that all one would have to do
is write 68851 MMU code + a couple of device drivers, such a thing is
firmly within the realm of possibility.  I generally have a lot more
respect for Sun's version of Unix than Unisoft Unix (A/UX folks?).  With
Sun's Unix, you would automatically  pick up access to their
applications code base, have really good  network + NFS code, NeWS/X
ports, good compiler technology, etc.

Anyways, I would like to hear what people think.  If you're wildly
enthusiastic and would like to help out, I would be very interested in
hearing from you!

                Rick Spanbauer
                SUNY/Stony Brook


------------------------------

From: [e-mail] (David Phillip Oster)
Subject: Re: What is .Bout for?!?
Date: 8 Oct 87 18:00:57 GMT
Organization: School of Education, UC-Berkeley

You've uncovered a bug in someone's software. The name ".BOut" not
".Bout" would cause the serial driver (printer port) to be opened for
ouput. Driver names, unlike filenames, are case significant.

The Macintosh User Interface Guidlines state that users should not be
allowed to create files with leading "." characters in their names. For
example, if the user tried to save a file as ".Sony", it could open the
floppy drive as a raw device and destroy the directory.  Most programs
have a bug in that they don't check for this and tell the user to type a
different name, one without a leading ".".

By the way, on the subject of saving files, I was talking to a niave
user the other day, and she was confused by the error message "The disk
is full, please use a different disk." She said, "I hit 'Save', I don't
understand." I told her that if you selected "Save As..." she would get
buttons to change drives and eject disks.

I got to thinking about her confusion. Two points to make:

1.) Software that confuses people is buggy in the user interface.

I also went back to all of my software and rewrote the error handler so
if the error condition calls for using a different disk, or ejecting the
disk to change the position of the write protect tab, it automatically
falls into Save As, with a diagnostic message dialog window on the
screen below the Save As... (SFPutFile) window.

It would be nice if other developers did the same.

----------------------

2.) Rule of Thumb: The real people who use our software are dumber that
you would possibly believe.

That isn't really true. Really they are busy, interested in something
else, and they don't have decades of computer reflexes built up. They
find computers useful, but not interesting enough to want to learn about
computers instead of use that learning time to do something else.  They
are violently frightened of making a disastrous mistake, and from their
point of view disastrous mistakes happen to them all the time.

They don't understand the word "debugging" and don't have the skills the
word implies for coping with misbehaving systems.

They turn in bug reports like "It is refusing to print Chapter 2."
instead of "The 'Print File' printer scroll file wants to be larger than
the amount of free space on my system drive. How do I get the software
to use smaller disk temporary files or write the print file to a
different drive?"

Cultivate a few naive user friends. You'll learn about flaws in your
software designs that your internal mental processes for coping with
computers filter out before they reach your conscious mind.

--- David Phillip Oster            --A Sun 3/60 makes a poor Macintosh II.
Arpa: [e-mail] --A Macintosh II makes a poor Sun 3/60.
Uucp: {uwvax,decvax,ihnp4}!ucbvax!oster%dewey.soe.berkeley.edu

------------------------------

From: [e-mail] (Dave Fritzinger)
Subject: Cricket Graph bug?
Date: 8 Oct 87 12:17:21 GMT
Organization: Public Health Research Institute, NYC, NY

Has anyone else seen this bug in Cricket Graph 1.1 with System 4.1 and
Finder 5.5?  Set up 3 columns of data, and try to do a "Double Y" plot,
and "Bang",  Instant Bomb with an ID = 02.  When you move the same data
file and copy of Cricket Graph to a disk with system 3.2 and Finder 5.3,
it works ok.

Is there anyone out there from Apple or Cricket Software who can explain
why this happens and offer a patch so that it doesn't happen?  Is this
due to be fixed in some future version of either the system or of Graph?
Help!! I really like Cricket Graph, and I really like the new system
and finder, but since I have to do quite a few double Y plots, I cannot
use them together.

Any help will be appreciated
David C. Fritzinger allegra!phri!fritz
PHRI 455 First Ave. NY, NY 10016
212-578-0855

------------------------------

From: [e-mail] (manic pop thrill)
Subject: comments on tape backup sold by `apda' requested
Date: 8 Oct 87 18:43:49 GMT
Organization: the billy and the boingers appreciation society

does anyone have any experience with the tape backup listed in the
recent `apda-log update' mailed out by `apda'?

thanks,

dsc

`they're so good at making soldiers,
 but they are not as good at making men'

------------------------------

End of Usenet Mac Digest
************************